Unix Service

This software contains two separate programs.  An administrator user interface, and a scheduler engine program which runs in the background.  By default, the scheduler engine in the background is not started with the 'nohup' command.  Hence, when you logout, the scheduler may shutdown.  By using the 'nohup' command to launch the scheduler engine, the scheduler engine will keep running after user logout.

Restart engine using launch code
You can re-launch the engine using the 'Restart engine using launch code' button.  This automatically shuts down the current instance of scheduler engine. Then, the engine is restarted, using the new 'nohup' code.

Recommended nohup launch code
The recommended command to launch the engine using 'nohup', is shown in the text box.  You can edit it as you wish.

Save code and always launch scheduler engine using this launch code
Select this checkbox, if you wish to always use nohup, to launch the scheduler engine.

Important Notes
1) If you are re-launching the scheduler engine, through a script or from a terminal, make sure that you shut down the scheduler engine, through the user interface first.
2) If launching Engine from command-line/script, start dir should be software install folder. Please 'cd' to the software install folder first.

Default Scheduler Engine Launch Code
If you used the install with JVM:
jre/bin/java -Xrs -cp .:help:hitek.jar:mail.jar:activation.jar:net.jar: .............. com.hitek.engine.Engine
or if you used the install without JVM and java is in your path
java -Xrs -cp .:help:hitek7.jar:mail.jar:activation.jar:net.jar: ............... com.hitek.engine.Engine

Look in the main install folder.  All the .jar file names in the main install folder should be added after net.jar: